Monster Media 1996 #15/Monster Media Number 15 (Monster Media)(July 1996).ISO/modem/bgfax160.zip/WHATS.NEW

Text File | 1996-06-22 | 27KB | 528 lines

Changes between BGFAX 1.60 and BGFAX 1.55                   SAT 21 JUNE 96
=========================================                   ==============

This 1.60 release has been in the works since February.  Over 75 changes,
bug fixes and new features have been made since BGFAX 1.55.  Rather than
list every single change as is usually done, I will only list the new
features and significant bug fixes.  For a complete list of changes, check
the "What's New" link on my web page.

We now have a U.K. registration site!  See REGISTER.UK
Compuserve SWREG registrations!  See REGISTER.FRM for more info
_____________________
BGFAX general changes
~~~~~~~~~~~~~~~~~~~~~
1. BGFAX no longer needs an environment variable.  If the "BGFAX"
   environment variable is not found, the BGFAX.CNF file will be looked
   for in the same directory as BGFAX.EXE.  Any use of the "BGFAX"
   environment variable will override this new logic.

2. Have optimized the communications/timeslice routine in the DOS version
   somewhat.  The DOS version should no longer take up 100% of the CPU when
   receiving or transmitting a page under OS/2.  Also, the DOS version
   should run more smoothly with both DesqView and Windows.  (CPUUSE.EXE
   for Windows 3.1 reported 4% usage when BGFAX/DOS is waiting for a call,
   14% during page receive, and 38% spikes during interpage negotation.)
   A major problem with BGFAX 1.55 running in "slow motion" under DesqView
   has also been fixed.

3. Changed OS/2 version so that it now works with IBM's stock COM.SYS driver.
   Previous versions of BGFAX2.EXE would only work with Ray Gwinn's SIO.SYS.
   Now, it can work with both.

__________________________
Changes in BGFAX send mode
~~~~~~~~~~~~~~~~~~~~~~~~~~
1. BGFAX /SEND mode can now send TIFF-Class-F files!  This is a very nice
   addition, since it allows much greater flexible in what documents are
   sent.  I tested sending TIFF-Class-F files made from BGFAX, Faxworks/2,
   and Word Perfect 5.1+/DOS, and all the documents faxed correctly.
   (BGFAX has had TIFF-Class-F receive capabilities for nearly a year now,
   and VIEW has had TIFF-Class-F viewing capabilties for several months
   now, but this is the first time /SEND has been able to process them.)

2. Numerous problems with Class 1 mode have been fixed.  Problems including
   not being able to transmit more than one page on some modems, non-stop
   failure to train errors, etc.

3. BGFAX /SEND mode will now create a SEND.DAT file after BGFAX finishes.
   The file will look like this:

FaxFilename 2pages.fax
FaxTelephoneNumber 7138939124
LastPageSuccessfullySent 2
TotalNumberOfPages 2

   This is a regular ASCII file, which contains information about the last
   fax sent, including (most importantly) the last page successfully sent.
   To use this information, you would need to write a program to examine
   and see if "LastPageSuccessfullySent" is equal to "TotalNumberOfPages".
   If not, this indicates a transmission failure, and you will need to
   resend the fax using the /SP:lastpagesuccessfullysent+1 logic, so that
   you need not resend the entire fax.

   This may also be useful on some of the buggier fax modems, where they
   (sometimes) do not return a successfully condition upon sending the
   last page, even though it was really sent.  What you would need to do,
   is see if the LastPageSuccessfullySent is one less than the
   TotalNumberOfPages, if so, you can "assume" (big assumption) that the
   last page might have actually gotten through even though the modem
   reports to BGFAX otherwise.

4. New BGFAX command line switch /NX
   This tells BGFAX that when sending faxes on Class 2 modems to "not
   wait for the initial XON" to be received.  This might be necessary
   on some older Intel(GVC OEM) fax modems.  Do not add this switch
   unless failed attempts in the BGFAX.LOG indicate "initial xon not
   received".

_____________________________
Changes in BGFAX receive mode
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. BGFAX.EXE now uses a different interrupt with NFAX.COM since the interrupt
   used in the last version caused troulbe when running in OS/2 DOS boxes.
   If you use the /NF switch on BGFAX, be sure to that you replace any old
   version of NFAX.COM with the 1.60 version, and reboot the system.  (NFAX
   is a TSR program that puts the word "FAX" on the screen when any incoming
   faxes are received.)

2. Fixed a major bug relating to saving files in TIFF-F format.  Anybody
   telling BGFAX to save in Faxworks format should immediately upgrade to
   this release.  The problem was that many faxes were getting scrambled
   because the byte-alignment filter in BGFAX was not working very well,
   resulting in faxes containing 50% bad scan lines.
   (Remember Z=ZFAX format, Q=QuickLink II format, F=TIFF-Class-F format)

3. New BGFAX command line switch /NT
   This tells BGFAX that when receiving on Class 1 modems to "not
   check training".  Starting with BGFAX 1.60, the training information
   will be checked, and if more than 25% of the data is "bad", BGFAX
   will force the remote fax machine to step down to a lower speed.
   The /NT will override the retrain.

4. DOBBS.BAT and DOBBS.CMD will now have the PID number appended to them
   when BGFAX is running in /HOST /PID:nnn mode.  i.e., /PID:4 will cause
   BGFAX to make DOBBS4.BAT files and BGFAX4.LOG files to keep things from
   getting "confused".

5. BGFAX will now honor the FaxWorks's FAX.IDX file.  This is a standard
   ASCII text file that will be present in the receive fax directory.  If
   BGFAX finds it, it will find out the last fax number that FaxWorks thinks
   it has received, and use that as the maximum fax number.  BGFAX will
   also update the FAX.IDX file.

6. New TSR program ATOTSR.COM might be required if you are receiving in
   Class 1 mode with some Fido mailers.  See the ATOTSR section in BGFAX.DOC
   to find out if you need to use it.  If you tried to setup BGFAX before
   and noticed the word "DATA" would pop up on the screen with your Fido
   Mailer but you never got a "CONNECT nnnnn" message from the modem, you
   are probably need to use ATOTSR.COM.

___________________
Changes in VIEW.EXE
~~~~~~~~~~~~~~~~~~~
1. VIEW.EXE has a new feature when you are in page-view mode.  Alt-J
   and Alt-G will now allow you to jump ("goto") a specific page number.
   So, if you bring up page 1 and want to go to page 13, just hit Alt-J
   (or Alt-G, same thing since many people told me they prefered "jump"
   and some "goto", so I made everybody happy) and type in "13" at the
   prompt.  Note that if you save faxes in ZFAX format, the first time
   you use the "jump" function, a quick analysis of the fax will be
   performed.  On slow machines (less than 386), this may take a while.
   On files saved in QuickLink of TIFF-Class-F format, the jump should
   be instant.

2. VIEW.EXE now handles /PCX conversions differently.  It seems that NOBODY
   liked my convention of converting multiple page fax files into PCX files.
   (If you had a 3 page fax, it would make HELLO.PCX, HELLO.P02, HELLO.P03
   in the old version of VIEW.)  It has been reported to me that most image
   editing software is brain dead and it will not acknowledge a file is PCX
   format unless it has a "PCX" extension, so here is how things work now:

   "VIEW 2letters.fax /pcx" will create PAGE0001.PCX and PAGE0002.PCX.
   Notice that the filename base is completely missing from the target
   files.  I did this because I just personally HATE fax software that
   does a truncation to the base filename in order to stuff the page
   number at the end.  So, how will the image editing software know about
   these funny PAGE*.PCX files?  Well, know, VIEW will create a DOPCX.BAT
   file that says:

        CALL EXEPCX PAGE0001.PCX PAGE0001
        CALL EXEPCX PAGE0002.PCX PAGE0002

   So, you can now put the name of your image editing or OCR software in
   the EXEPCX.BAT file that you will produce, and pass the filename via
   the %1 variable (or %2 variable if you are using even brain-deader
   software that croaks if a PCX extension is given when the extention
   is already known to be PCX).

3. New VIEW command line switch /RF
   "Retain filename" mode will make VIEW convert PCX faxes using the
   naming convention used in BGFAX 1.55 instead of the new way.  A
   three page fax converted to PCX would come out as:
   FILENAME.PCX, FILENAME.P02, FILENAME.P03  (all three being PCX files)

4. VIEW.EXE will now automatically "flip" pages in a fax if you press
   Alt-F when viewing the first page.  This just saves you a keystroke
   on each page, since you will no longer have to hit Alt-F on any
   page except the first if someone sends you an upside down fax.

5. New VIEW command line switch /PL:nnnn
   This lets you refine the "page length" of a piece of laser paper, in
   the number of laser-scan lines.  Normally, VIEW uses 3380 scan lines
   for a piece of A4 paper, but I was told some A4 printers very, i.e.:
   Deskjet 500C A4 /PL:3170 or /PL:3320 is performation skip
   Deskjet 500 A4 /PL:3234
   Oki Laserline 6 A4 /PL:3411
   If you are using US paper size, this switch should not be necessary!

6. New VIEW command line switch /RH
   VIEW.EXE will now double the number of scan lines of a low resolution
   fax during a PCX and DCX conversions so that it works better with OCR
   software that might be expecting more pixels to work with.  To override
   this feature so that PCX and DCX conversions provide a one-to-one pixel
   conversion, use the new /RH switch (retain height).

7. VIEW now supports printing to 9-pin dot matrix printers.  Use VIEW /P9
   to set VIEW into 9-pin mode.  NOTE: In this mode, VIEW will print pages
   twice as long as they should be.  So, a 3 page fax will take 6 pages to
   print.  I've refused to support 9-pin printing in the past, because it
   is my opinion that faxes just are not worth printing to 9-pin printers.
   By printing one page as two, it allows us to get something printed that
   at least is readable.  If you still have a 9-pin printer you really need
   to go buy a 24-pin or laser.

_____________________________________________________________________
Changes in MAKEFAX (ASCII/PCX/DCX to FAX converter for sending faxes)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. MAKEFAX can now handle multiple input files!  Example...

        MAKEFAX cover.pcx+filename.txt+file2.txt output.fax
           or
        MAKEFAX @filename.lst output.fax

   Where "filename.lst" is a standard ASCII text file, with one filename
   per line.

2. MAKEFAX now supports 80-column and 132-column modes!  FINALLY!

         MAKEFAX filename.txt output.fax /80       80-column conversion
         MAKEFAX filename.txt output.fax /132      132-column conversion

   Remember that MAKEFAX will default to 100-column conversion.

3. MAKEFAX now supports DCX as a valid input file type.  (Recall DCX is
   a multi-page PCX file), e.g.,
       makefax sample.dcx output.fax
   or, makefax coverpg.pcx+notes.txt+document.dcx+signatur.pcx output.fax

4. New MAKEFAX command line switch /LR
   MAKEFAX, when converting PCX and DCX files to FAX mode will now "guess"
   as to what resolution flag to put in the fax header, so that BGFAX knows
   what to tell the remote fax machine about the resolution of the upcoming
   document.  If the PCX or DCX file has a page with greater than 1200 scan
   lines, it will assume the fax is to be marked as high resolution.  If
   less than 1200 scan lines, it will be assumed low resolution.  MAKEFAX
   can be forced to put a high resolution flag in the header with a /HR
   switch, and a low resolution flag with the new /LR switch.

____________________________________
Changes in FNTEDIT.EXE (font editor)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. FNTEDIT made more multi-tasking friendly.  It will now return time slices
   when waiting for input from the keyboard.

2. FNTEDIT was not always saving changes to the last character edited.  This
   should be fixed now.

#############################################################################

1.55          Mon 8 Jan 1996
----------------------------
1.54 release would not receive properly if running under a system that
was running with Novell Netware Lite.  Only BGFAX.EXE and BGFAX2.EXE have
changed since 1.54.

Changes between BGFAX 1.54 and BGFAX 1.50                    MON  1 JAN 96
=========================================                    =============

New features and bug fixes in VIEW.EXE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Have speeded up laser printing of faxes if you are using a laser printer
   that supports the PCL4 or PCL5 command set.

   Example PCL4 printers: HP LaserJet IIP, Deskjet Plus, Desket 500
   Example PCL5 printers: HP LaserJet series III and 4

   Switch    DPI    PCL  average number of bytes sent to printer per page
   ------  -------  ---  ------------------------------------------------
    /P37   150x150   3   207K
    /P38   150x150   4    60K
    /P39   150x150   5    48K  ( PCL5 not much gain over PCL4 at 150x150 )
    /P40   300x300   3   806K
    /P41   300x300   4   183K
    /P42   300x300   5    82K  ( Big gain! Ten times smaller than PCL3! )
    /P24   180x180  n/a  303K  ( Just for reference, Epson 24 pin dot matrix )
    /P25   360x180  n/a  604K  ( Same Epson )
    /P26   180x180  n/a  315K  ( The Canon BJ-200 )
    /P27   360x360  n/a 1257K  ( The Canon BJ-200, yes 1.3 meg/page :-( )

   How is VIEW.EXE able to make the amount of data sent to the printer so
   much smaller?  PCL4 allows the use of the PackBits compression method
   (HP calls it the "TIFF" method, but it is not TIFF).  The PackBits method
   is kind of an enhanced-RLE coding scheme.  PCL5 adds a 2D-like compression
   scheme, and BGFAX is not even using it to it's fullest extent.  (It would
   take some serious coding to use PCL5's Delta Row compression to it's
   fullest.)  VIEW uses Delta Row compression only when it needs to send two
   or more identical scan lines to the printer (which is the case when
   printing low resolution faxes.)

2. Fixed bank switching routine in VIEW.EXE that caused 1024x768 mode not
   to work on some computers.

3. VIEW now supports VESA 1280x1024 mode.  To view faxes in this mode,
   start view with the /1280 switch.  Alt-S (squeeze) will not function
   when viewing in this mode, because the image, for the most part, fits
   nicely on the screen (okay, you might have to hit right arrow twice
   to see the far right side of the fax.)

4. VIEW.EXE was not correctly viewing TIFF-Class F (Faxworks) image
   files if they had more than 1 page.  It should work correctly now.

5. Rewrote small parts of VIEW.EXE in assembly, for slightly faster operation.

6. VIEW will now spool to disk if all conventional and XMS memory runs
   out when loading the page image.  Things will become *SLOW* if this
   happens, although since most people have XMS, this should only rarely
   happen.

7. Enhanced /CGA display mode with respect to Alt-S.  If you "shrink" a
   screen in CGA mode now, the "shrink" mode will stay engaged as you
   pan around the screen.

8. If VIEW was viewing a PCX file that's x-dimension size was not a multiple
   of 8, the right corner of the image would have artifacts in it.  Fixed.

9. In old VIEW, if you were viewing a fax, and hit <F1> for Help or
   <Ctrl-Enter> to print just that page, when VIEW put the fax back
   on the screen, it would only put part of it back.  Fixed.

New features and bug fixes in BGFAX.EXE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1. New BGFAX command line parameters

   a. /NL       Do not create or write to the BGFAX.LOG file

   b. /SD       Do not put additional debug information into DEBUG.LOG
                (BGFAX 1.54 now defaults to use "debug" mode.  This
                parameter is needed to take 1.54 out of debug mode.
                The "FAX=DEBUG" environment variable is no longer used.)
                If you use /NL, you do not need to use /SD.

   c. /MO       BGFAX will only use monochrome colors when writing to
                the screen--useful for palmtop users.

   d. /NM       BGFAX will use "numeric mode" when talking to the modem
                in Class 1 /SEND mode.  This might be needed if you are
                sending from modems like the I-Modem.  Numeric mode
                basically puts the modem into ATEQV mode.

   e. /SL:nn    Add nn extra scan lines to the top of each page sent in
                /SEND mode.  Example: BGFAX /SEND file.fax [phone] /si:20
                BGFAX will add 20 blank scan lines to the top of each page
                as it sends.  Just adds extra white space, nothing special.

   f. /CI:xxxxx Check ID of remote machine before we /SEND the document.
                Example: BGFAX /SEND file.fax [phone] /ci:3_9124
                BGFAX will dial the remote fax machine, and make sure
                that a "3 9124" appears somewhere in the remote fax ID.
                Note that underscores (_) are used to represent spaces.
                If /ER mode is active, if the Check ID fails, BGFAX /SEND
                will exit with errorlevel 18.  If no /ER, if it fails, it
                will exit the standard error exit errorlevel 1.  How is this
                useful?  Well, say someone gets call forwarding on their fax
                line, and they have to forward their number to an alternate
                fax machine for a week while their fax machine is repaired.
                The remote fax machine is probably programmed with an
                alternate remote ID, and BGFAX /SEND will abort when it
                realized the remote ID does not match what it should, in
                the case that you need to send very confidential documents.

2. BGFAX /SEND mode will no longer perform the "analysis" phase when
   sending QFX files, since the information BGFAX is looking for is
   really already in the QFX header.  (Regular ZFAX-style FAX files
   will continue the scan.)

3. Believe I found the problem with BGFAX leaving behind BGFAX.$$$ files
   when receiving.  It should now call it FAXnnnn.FAX (or whatever) like
   a successful fax reception even if it timeouts or otherwise fails.

4. In Class 1 mode, occasionally BGFAX would hit a weird fax machine that
   keep requesting one retrain right after another.  The other fax machine
   would never timeout, and this could go on for hours.  Now, I've changed
   BGFAX so that if more than six FTT frames (retrains) happen, it will
   abort with a timeout condition.  If /ER (extended results) mode is active,
   this condition will be errorlevel 19 (too many retrains).

5. Class 1 mode is now sending about 100 null bytes at the end of each page
   after the RTC, because some times the other side was not always receiving
   the RTC sequence, so the these "extra bytes" should help.

6. Class 1 mode should now be able to handle reception of invalid
   HDLC frames by asking the remote side to resend them (in case of
   a line noise error).  If this happens, you'll see a "REQUESTING
   FRAME REPEAT" appear on the screen and in the log.  It is very
   hard to duplicate when this happens, so I was unable to test this
   code to see if it fixed it or not.

7. BGFAX would not abort if the /HOST mode "extra id[]" field contained the
   keyword "ERROR".  Fixed now.

New features and bug fixes in MAKEFAX.EXE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. MAKEFAX has a new command line parameter, /PL:nn where /PL can be used
   to override the number of lines per page, useful for people in countries
   that do not use US-paper sizes.  e.g., MAKEFAX HELLO.TXT OUT.FAX /PL:70
   Would use 70 lines of text per page instead of the US value of 66 lines.

2. If MAKEFAX was converning a PCX into a FAX where the PCX x-dimension size
   was not a multiple of 8, things went wacko.  Now fixed.

3. Changed MAKEFAX so that it handles strange ASCII situations in a more
   elegant manner.  (Someone had a test file where instead of each line
   terminated by a CR/LF, it was a LF/CR.  MAKEFAX no longer goes beserk
   when this happens.)

#############################################################################

Changes between BGFAX 1.50 and BGFAX 1.47                    THU 17 AUG 95
=========================================                    =============

NOTE: If you receive faxes in a directory other than your BGFAX directory,
      you must move FAXIN.LOG into the directory where all the faxes are
      received before installing 1.47 Beta!!!

MAKEFAX.EXE show now properly handle page breaks (Ctrl-L) when converting
ASCII files to FAX.

New Features in VIEW.EXE
~~~~~~~~~~~~~~~~~~~~~~~~
1. VIEW supports XMS memory now!

2. VIEW can now view TIFF Class F (Faxworks, Word Perfect, QLII *.REC,
   etc) files, as well as 2-color PCX and DCX files.

3. Some new magnification factors have been added.  Use Alt-S to cycle
   through the scales when viewing a fax.

      BGFAX starts in full mode (no on-screen compression)
      Alt-S once, makes the image 1/3 width
      Alt-S twice, makes the image 1/3 width "bold"
      Alt-S thrice, makes the image 1/2 width
      Alt-S 4 times, makes the image 1/2 width "bold"
      Alt-S 5 times, cycles back to the original full mode (no width compress)

   The "bold" is just a different algorithm for the on screen compression,
   which sometimes makes it easier to read, other times, it makes it harder
   to read.  (That's why I leave both options in VIEW.)

4. When you are viewing the fax, if you want to print a particular page
   rather than the whole fax, simply press Ctrl-Enter to print the page
   you are currently viewing!

5. VIEW would detect the video adapter on startup, and on many systems
   would identity it as "SVGA" (800x600), but would fail to display images.
   Since I have not yet been able to debug this, I am now making VIEW only
   auto detect up to VGA adapters.  To use 800x600 mode, use /SVGA on the
   VIEW command line.  To use 1024x768, use /1024.

New VIEW.EXE command line switches...

/P39     Use PCL (laser printer) 150x150 dpi mode.  Useful with laser
         printers with small (512K) memory, and for people who want
         super-fast printing.  (/P40 PCL mode is 300x300 dpi).  Only
         1/4 the amount of data sent in /P40 mode is sent in /P39 mode.

/DCX     VIEW filename.fax /DCX will convert the fax to a multipage DCX
         file.  DCX is nothing but a black-and-white multipage PCX file.
         See the BGFAX.DOC for a quick description of the DCX format.
         Also, <F3> at the VIEW main menu is available for FAX->DCX.

/HS      When VIEW creates PCX or DCX files, it will "half size" them so
         that they are only 864 pixels wide (similar to the way Quick Link
         II performs FAX->PCX) instead of the normal 1728 pixels wide.

/LP      Select legal paper size during printout (Ex: VIEW /P40:LPT2 /LP)
         Only valid if using laser printers (/P39 or /P40 mode)

/A4      Select A4 paper size during printout (Ex: VIEW /P40 /A4)
         Only valid if using laser printers (/P39 or /P40 mode)

/NF      If you are using the NFAX.COM TSR program, if you place the /NF
         switch on the VIEW.EXE command line, if any "FAX" message appears
         on the screen, it will turn it off.  (Same as FAXOFF.COM program.)

New Features in BGFAX
~~~~~~~~~~~~~~~~~~~~~
1. Improved Class 1 performance.  (BGFAX now follows the timing specs in
   T.30 better.)

2. Improved BGFAX/2 screen write speed significantly.  Fixed a bug in BGFAX/2
   /HOST mode which caused Maximus/2 users problems when downloading files.

3. In /HOST mode, if a non-error correcting call came in, the "%4" variable
   in the DOBBS.BAT file was not being set to anything.  Now, non-EC calls
   will have that variable set to "N/A".  I think this is the way FD and IM
   do it.  Let me know if this is wrong.  Note: You _might_ have to adjust
   your FBBS.BAT files regarding this, depending upon BBS software.

4. A new BGFAX.CNF entry for /HOST mode... Example: vm=CONNECT VOICE

   If the "CONNECT VOICE" string is encountered, BGFAX will exit with an
   errorlevel of 8.  You can also use this will distingtive ringing modems,
   i.e., vm=RING B to have BGFAX exit with errorlevel 8 if it encounters
   the second RING cadence pattern (must have a distingtive ringing modem
   and feature from the phone company, as well as some kind of voicemail
   application that supports a "hot" port.)

5. If you are using a ZyXEL 2864I (ISDN) and want to /SEND faxes, you will
   need to put a "ss=AT&O0" in your BGFAX.CNF file.  That will tell BGFAX
   to send using the Fax/Modem DTE channel instead of the ISDN DTE channel.

New BGFAX.EXE command line switches...

/SP:nn   Tells BGFAX to start sending pages from page number nn.
         Example: BGFAX /SEND OUTPUT.FAX [phone] /SP:14
         Tells BGFAX to send the OUTPUT.FAX file, starting at page #14.

/C2      For modems such as the ZyXEL, forces BGFAX /SEND mode to use
         Class 2 mode for fax sending instead of Class 2.0 mode.
         Examples: BGFAX /SEND OUTPUT.FAX [phone] /C2

The /DW and /OU switches have been removed.

##############################################################################

Release History
~~~~~~~~~~~~~~~
Version      Date              Comments
-----------  ---------------   -------------------------------------
Alpha 4      Fri 21 May 1993   (first open alpha test)
Beta 1       Sat 19 Jun 1993   (first open beta test)
BGFAX 1.06   Tue 14 Sep 1993   (initial public release, DOS version)
BGFAX 1.07   Sun 14 Nov 1993
BGFAX 1.08   Sun 21 Nov 1993
BGFAX 1.09   Wed 22 Dec 1993
BGFAX 1.10   Mon  4 Jan 1994
BGFAX 1.21   Fri 25 Mar 1994
BGFAX 1.30   Sat 11 Jun 1994
BGFAX 1.36   Sun 25 Sep 1994
BGFAX 1.40   Sun  1 Jan 1995   (initial public release, OS/2 version)
BGFAX 1.47   Mon  2 May 1995
BGFAX 1.50   Thu 17 Aug 1995   (released at ONE BBSCON TAMPA)
BGFAX 1.54   Mon  1 Jan 1996
BGFAX 1.55   Mon  8 Jan 1996
BGFAX 1.60   Sat 22 Jun 1996